Skip to content

Conversation

@fern-api
Copy link
Contributor

@fern-api fern-api bot commented Feb 10, 2026

This refactoring removes user_id fields from various API response types across the codebase and simplifies the construe code system upload interface. These changes improve API consistency and reduce unnecessary data exposure.

Key changes:

  • Remove user_id fields from ChatMessageTemplate, ChatSessionTemplate, FhirProviderTemplate, and other response types
  • Simplify construe upload interface by consolidating UploadRequest types and removing discriminated union
  • Update upload API documentation to clarify asynchronous processing behavior
  • Remove async parameter from upload requests (now always asynchronous)
  • Add name and version fields to ConstrueUploadCodeSystemResponse for better tracking
  • Update all test cases to reflect the simplified interface and removed fields

🌿 Generated with Fern


Note

Medium Risk
This is a breaking API surface change for SDK consumers (removed fields and changed uploadCodeSystem request/response types), requiring downstream code updates, but it doesn’t alter auth/transport logic.

Overview
Bumps the TypeScript SDK to 6.0.0 and removes user_id from multiple generated API response/template types (agent chat messages/sessions, FHIR provider templates, summary templates, MCP server/tool responses, workflows), reducing exposed user-identifying data.

Refactors Construe code-system uploads by replacing the prior format-discriminated UploadRequest* union with a single construe.UploadRequest type, dropping the async flag (uploads are now documented as always async) and updating docs/tests accordingly; upload responses now also include optional name and version fields.

Written by Cursor Bugbot for commit 7d52ae3. This will update automatically on new commits. Configure here.

…terface

This refactoring removes user_id fields from various API response types across the codebase and simplifies the construe code system upload interface. These changes improve API consistency and reduce unnecessary data exposure.

Key changes:
- Remove user_id fields from ChatMessageTemplate, ChatSessionTemplate, FhirProviderTemplate, and other response types
- Simplify construe upload interface by consolidating UploadRequest types and removing discriminated union
- Update upload API documentation to clarify asynchronous processing behavior
- Remove async parameter from upload requests (now always asynchronous)
- Add name and version fields to ConstrueUploadCodeSystemResponse for better tracking
- Update all test cases to reflect the simplified interface and removed fields

🌿 Generated with Fern
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

export type { GetConstrueCodesCodesystemSearchTextRequest } from "./GetConstrueCodesCodesystemSearchTextRequest.js";
export type { GetConstrueCodesSystemsCodesystemExportRequest } from "./GetConstrueCodesSystemsCodesystemExportRequest.js";
export type { GetConstrueCodesSystemsCodesystemRequest } from "./GetConstrueCodesSystemsCodesystemRequest.js";
export type { UploadRequest } from "./UploadRequest.js";
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

export type prevents runtime access to Format enum values

Medium Severity

The UploadRequest in requests/index.ts is re-exported with export type, which strips the runtime Format const values (Csv, Json) from the namespace. SDK consumers can't use UploadRequest.Format.Csv at runtime — the const is effectively dead code. By contrast, similar enums like GetCodeSystemDetailResponse.Status in types/index.ts are exported with export * and remain fully accessible.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants